File: 1601503611967.png (241 KB, 600x578)

241 KB PNG

Poop

If anyone has WDK 8.0 could you upload the nmake2msbuild.exe somewhere?

>>78804671
Might also need C:\Program Files (x86)\Windows Kits\8.0\bin\conversion folder too

>>78804671
Here's some older versions of WDK:
>https://docs.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads#step-2-install-the-wdk

File: 673d00466436c13b8ba8ed44a(...).jpg (18 KB, 292x368)

18 KB JPG

>>78804457 (OP)
Can I ask some dumb questions? What practical uses will this source code likely be put to? So far it seems people have been able to build the working OS again, which is nifty, but will we see modified XP builds updated to be more secure and compatible with modern software? how long could such a project take? Is this even likely to happen considering that this code is illegal and can't be worked on openly? Is the work being done here currently moving toward this end?

>>78805057
literally fucking nothing. the retard autists from this board have been jerking themselves off to this shit and none of it fucking matters because the only shit it will ever amount to is making losers look cool in desktop threads. Fuck all of you.

>>78805057
There's been some small updates made to it, to get newer programs working etc. I wouldn't be surprised if some private efforts were being made to do something more substantial.

>>78805119
You are and fucking piece of shit go away from this thread as we are all fucker. Idiot fuck you maroon linux lover that are here only to troll people. Piece of shit. You are pathetic maroon and you know it.

what's new under the sun

>>78805599
trolls are back at us that is what this afternoon and night is insulting us and speaking about stupid tings

>>78805599
Someone was working on a missing.7z for checked builds but he disappear

>>78805057
>practical uses
None, really. It's mostly for fun.

any ATMs still running XP out there?
articles from 2 years ago and 6 years ago
www.itproportal.com/news/security-firms-warn-that-most-atms-still-run-windows-xp/
www.computerworld.com/article/2700811/95-percent-of-atms-run-windows-xp--here-s-everything-you-need-to-know-about-the-security-threat.html

Is there any VM for IA64? If we could run the IA64 build it might help us figure out wow64 crap, which it seems we need for amd64 support.

>>78806283
Looks like QEMU 2.11-rc1 dropped IA64 support, so maybe anything before that supports IA64. No idea how good, though. Also found another sim supposedly at http://www.gelato.unsw.edu.au/IA64wiki/SkiSimulator but link is dead

>>78806584
It seems that 2.11-rc1 dropped ia64 **host** support, and guest support never really seemed to exist

>>78805939
As far as I have seen, Diebold and Siemens ones are. But they run stripped embedded sku, not retail.

>>78806283
Simics seems to have ia64 support, not sure where to get hold of it though

Bump.

Almost got the missing chk pack ready, just need to get hold of xpsp1sym_x86.exe & xpsp1sym_x86_chk.exe now so I can add the last few pdbs to it.

Is there anyone here building x86chk that can test it?

>>78808069
I thought XP could not be built yet? I'm using srv0rtm checked

>>78808239
srv03rtm checked is fine, I only needed xpsp1sym because some client files like MSN6.exe came from XP SP1 iso, there's only like ~30 or so files that came from SP1 tho, rest are from win2003 ISOs

Got the pack ready now, both fre+chk files comes to only 619MB, not too bad. I'll start upping in a sec

File: file.png (19 KB, 463x231)

19 KB PNG

Okay, new missing 7z is up:
>win2003_x86-missing-binaries_v1.7z
https://gofile.io/d/HMjsfq

Contains missing files for both x86fre & x86chk, taken from the fre/chk ISOs.
Base edition is enterprise for both (since chk is only available in enterprise edition I figured I'd use it for fre as well), so you'll probably need to use enterprise CD-key.

Files that weren't available in any win2003 iso (msn6.exe, and other client stuff) were taken from XP SP1 (afaik the missing-v8.7z took these files from XP RTM, so the files in here should be a little newer, and closer to win2003's versions)

PDBs inside symbols folder are mostly taken from win2003 symbols packs except a few files that came from XP SP1, haven't checked if all the symbols actually match up with all the binaries yet though.

I haven't tested all editions yet, would appreciate anyone trying them out. (maybe this can help solve the chk login assert?)

In case anyone cares, order of ISOs used to obtain the files:

(x86chk only) Win2003 Enterprise x86chk
(x86chk only) WinXP SP1 Pro x86chk
Win2003 Enterprise x86fre
Win2003 Datacenter x86fre
Win2003 Standard x86fre
Win2003 Webserver x86fre
Win2003 SBS x86fre
WinXP SP1 Pro x86fre
WinXP SP1 Home x86fre
WinXP x64 Pro amd64fre (for srv_info.chm)

>>78808343
Oops, stealth updated to v1a because I accidentally left in some pdb that wasn't needed.
(if you get asked to replace any files when using this pack, pls let me know - replacing folders is fine though)

Also just tested out x86chk-srv, no BSOD assert at gui setup at least, still installing though so not sure if actual boot works yet.
Maybe it was replacing some fre file with chk version that fixed it, or maybe because I'm using exinit.c/systime.c instead of the fre .obj files, not sure, at least it's working the same as official chk release now though :)

File: file.png (16 KB, 640x480)

16 KB PNG

>>78808481
Finally got thru setup, and yep, x86chk setup & normal boot both work fine without needing debugger

>>78808343
One more stealth update to v1b, removes another few files that weren't needed.
Hopefully last update for now, unless someone finds an issue with it.

>>78804457 (OP)
The centralizer-threads page needs to be updated. Latest thread on there is from over a week ago.

>>78804521
Someone needs to make a better poop edit, sort of like how the old pee edit was made to look like actual piss. This looks more like mud than it does shit.

>>78805057
i would absolutely love to see a native ARM build of windows xp. ripping out the crypto subsystem and replacing it with something like openssl would be pretty awesome too. so far i haven't done more than build a 2k3 image, but if i was a neet i'd sink some serious hours into messing with this stuff.

Found this linked in an old /wxp/ thread, thought it might be useful to see again. Helps porting drivers/software/etc to XP/Srv2K3.
https://msfn.org/board/topic/181615-ntoskrnl-emu_extender-for-windows-xp2003/
https://msfn.org/board/topic/176605-compatibility-layers-for-xp/
https://katahiromz.web.fc2.com/vista2xp/en/
Credit to >>77985805

>>78805057
No.

>>78805235
Nothing was done that can't be done without the source code.

>>78808792
This will literally never happen. It's way, way, WAY beyond the capability of the /g/entooman. You'd have more luck getting a caterpillar to build an FTL starship.

>>78809082
ARM support was difficult enough for Micro$haft, /g/entoomen couldn't do it if they tried.

>>78809082
you're probably right, but i can dream

>>78806283
I had asked this question like 1 month no "good" answer yet

>>78808239
I have a checked build done without any missing file

>>78809949
Because there is no IA-64 emulator that would allow you to launch Windows on it.

Hey, I'm looking for smart people who know how reverse engineering work or who can program in C or assembly. Lets do something great together! Unfortunately I'm not going to tell you details here thanks to a lot of idiots coming around. If you done some work here and want to continue together, send me mail at "ntguy at protonmail" and write what you already did and what you can (programming, reversing, graphics)

>>78808792
You are welcome to contribute and write from scratch part of the kernel that is missing. To support ARM we need a major update to all the main components aka probably we as community we will never be able to do that.

>>78806283
I already compiled amd64 but there is some drivers missing that i can't find.Right now im stuck at amd64 text install.

Is it possible to get XP to boot with the Vista (or Vista beta) ntoskrnl and hal?

>>78810168
off cours eno idiot, why you would do that? And secondi is not like linux where you can just switch the kernel the other components require the kernel to have the exports and in vista changes were made. Your question is really dump, is like I have car can I make it a ferrari if I use the ferrari motor?

>>78810168
There are more things coupled tightly with kernel, not just hal. Vista is NT 6 and implements new driver model, so you will need Vista drivers as well. Then other components that work in kernel mode will have problems as well, probably whole GDI, WIN32K kernel-mode part, and so on. You will end up with Vista anyway. Stupid idea.

>>78808343
Mb smaller than what I was getting when I The only think I noted is that the final image is 70Mb smaller than what I was getting when I was using the fre files.

>>78810382
I try to write again because fuking numkey was disbaled and mess up the text, fuck:

The final iso image (for xp image) is 70Mb small than what was the image made with the free missing files, but it seem to install fine anyway. Also you have used enterprise pid so to install we need to use enterprise key and not standard.

>>78810532
does it install 2003 enterprise?

>>78810863
If you build enterprise sku iso then yes.

What VMs do you use to test your built ISOs?

VirtualBox runs like a hag

>>78811128
Im using VirtualBox it's works fast only with fully disabled hyper v

File: Снимок.png (76 KB, 979x874)

76 KB PNG

Almost fixed amd64 pro sku it's only missing 48 files

>>78811287
Didn't think about disabling Hyper V cheers!

bump

>>78810005
Go stand in a train wreck, namefag.

>>78808860
Katahiro is one of RetardOS devs.

File: Capture.png (31 KB, 984x184)

31 KB PNG

>>78804457 (OP)
I can't seem to get through the postbuild without it throwing errors towards me about Winlogin, I used the winlogin200X provided by OP on my build. Is the Winlogin provided in the OP not working with the source currently or is it my retarded ass not knowing how to build from source correctly?

>>78812603

shut up trolling idiot and let them work with all anons

>>78812849
Winlogon from win 2000 sources always gives that error i think you can ignore it or use winlogon exe from missing 7z

File: 20201121_155336.jpg (492 KB, 1440x880)

492 KB JPG

>>78812849
It got answered a while ago, shame it isn't in the guide

>>78813720
I think it was to edit the sources.inc for winlogon not sure

>>78813320
Okay I'll try making some cd images with the compiled Winlogon and hope for the best..

>>78808788
this
>>78804521
can you post piss and period blood edits? I forgot to save from last thread.

bump for adobe photoshop source code

File: Screenshot from 2020-11-2(...).png (46 KB, 640x524)

46 KB PNG

>>78813765
The standard server key doesn't work anymore it seems.

>>78815213
yeah use enterprise he jut use the wrong pid.

>>78815285
That works, thanks man

>>78815339
I know it worked if you had read prev post I basically post the same problem and solution ahah

>>78814722
I think photoshop 1.0 source is avaible somewhere (too lazy to look it up), maybe it's on archive.org. It's written in pascal, I think.

Are all the boot image source in base/ntos/init ?

I can't find where the actual boot image is

>>78816358
What do you mean by boot image? if osloader or NTLDR then it's here base\boot\bldr i think.

>>78816358
Also i recommend this: https://en.wikipedia.org/wiki/Windows_NT_startup_process
it's has lot's of info about windows boot process

>>78816733
>>78816757
The 'Windows XP Pro' image on boot and thanks! I'll look into it

>>78817093
Then base\ntos\init\init.c DisplayBootBitmap function
base\ntos\init\logo.bmp - logo
base\ntos\init\protext.bmp - xp and pro text
For some reason bmp shows nothing but it has image idk how to load it correctly

>>78817340
Yeah I noticed the blank image as text, I even tried changing the logo but it is still the default logo

>>78817398
editing base\ntos\init\init.c works.
But i tried to change logo.bmp then i did bcz in base\ntos and it's not worked...
Idk what kind of black magic in these bmp files.

>>78817740
Same issues as me then, editing the source files is fine.. maybe the images are part of a pre-compiled obj? (But clean build should rid them right?)

>>78818204
just found out that boot.bmp should be logo.
Also found this tutorial to open these bmp files: http://users.telenet.be/Robvdb/how_to_change_bootscreen_XP.htm

File: Снимок.png (45 KB, 1142x481)

45 KB PNG

>>78818315
Color Palettes can be also found in anim.c file

>>78818315
>>78818377
Nice finds! Thanks alot Anons!

File: piss.png (251 KB, 600x578)

251 KB PNG

>>78813792
Period blood is in OP, here's piss.

File: Снимок.png (14 KB, 642x554)

14 KB PNG

Vista logo test

>>78810382
>>78810532
>70Mb small
Ah, think that might be the lang folder in the missing-v8 pack, didn't include that since postbuild seemed to be successful without it, but I guess ISO must still try copying them if they exist.

For fre you can maybe try copying in missing-v8s lang folder after copying in the new x86-missing-bins 7z, hopefully ISO should be closer to proper size with that.
That might work for chk too, but I'll look into getting the actual chk lang files from the chk ISO later.

What build produce PDB? chk?

File: file.png (6 KB, 285x109)

6 KB PNG

>>78819253
All builds do afaik

>>78819253
every build produces pdb files you can find them in D:\binaries.x86fre\symbols.pri

>>78819269
ok, thanks
another question, which microsoft official build can be used with pdb?

>>78819301
5.2.3790.srv03_rtm.030324-2048 (Retail Server 2003)

>>78811307
Last anon to work on amd64 just edited layout.inf to remove those files since there's no amd64 versions of them.
The official x64 ISO's layout.inf also had them removed too IIRC. Might be a good idea to reference/compare with that.

>>78819348
>>78819334
ok, how do you find pdb for this?

>>78819497
https://blog.csdn.net/chubaisheng8627/article/details/101018719
lists pretty much all the XP/2003 symbols packs, links are dead but web.archive.org works sometimes

>>78819582
use the march 2006 web.archive.org capture if you want to download the full package btw, otherwise it'll probably cut out at 100MB

>>78819582
thanks but i mean generally, how to find them? eg for vista or 7?

>>78819348
Thanks for info im going to try this with
mergedcomponents\setupinfs\layout.inx file

>>78819684
there used to be a page on MS site that listed them all but they took it down now, so only way to find them is googling for eg "windows 7 debug symbols" and hope you find somewhere that has a link

How do I find the product key for an ISO that I built? There's not one in the guide for XP Pro i386. Is there a way to disable the need for a key altogether?

>>78819887
Standard Edition: M6RJ9-TBJH3-9DDXM-4VX9Q-K8M8M

>>78819887
You'll either need standard key or enterprise key, depending on which missing.7z you used

>>78819981
why don't you build datacenter?

>>78820011
you can if you like, but missing.7z are only using pidgen.dll from standard/enterprise, if you really want to use datacenter key you'll need to grab pidgen from a datacenter iso

>>78820024
>pidgen.dll
What is it responsible for? Just installation key or anything else?

>>78820035
yeah think so, someone posted code that can build a cracked pidgen that allows any key a while back, but winlogon would refuse login because WPA crap built into winlogon would detect bad keys

now that we have our own winlogon src without WPA maybe it'd work fine though, but I don't think anyone tried it yet

>>78820035
Licence key checking

>>78820050
I'm willing to test that if you provide link to cracked pidgen

>>78820063
just found it luckily
https://archive.rebeccablacktech.com/g/thread/78212123/#78242359
in that thread you can see what happens with normal winlogon.exe too, but with our winlogon200X replacement it should work fine hopefully

>>78820076
For schizos that have user.js enabled (or just don't send referrer header), you need to enable the sending of the referrer header to download the file.

Do I have to run postbuild after each modification? Or is it only after the first build?

File: .png (97 KB, 1050x742)

97 KB PNG

>>78819261
>4 files
pfft, try grabbing the whole https://msdl.microsoft.com/download/symbols/packages/ folder next time

just need to get hold of the symbols ISOs and maybe I'll post this up somewhere

>>78820409
for the CD folders to get updated you'll need to postbuild again yep
it shouldn't take as long as the first postbuild though, uses bindiff to see what files changed etc. you could use -sku:srv argument to only process the sku you're working with too.
someone posted some env vars you can set to speed up postbuild as well but I don't have them saved anywhere

>>78820459
Thanks! I was worried that I would have to wait another half hour for just a couple of files.

>>78820409
>>78820459
If its modifications to source files, you will have to at least rebuild that folder containing modified source

>>78820437
hm damn, trying to compress the exe's doesn't really compress at all, 7z ends up at 5GB, because they're already compressed I guess

I could extract the EXE, and the cab inside the EXE, and then compress the extracted pdb files, will probably bring down the size a lot, but then I wouldn't be uploading the original symbols packs...

maybe I'll just make a list of the web.archive.org urls I used to download them

File: 20201122_004557.jpg (506 KB, 1440x1279)

506 KB JPG

Has anyone tried this yet for any of the software in the source?

Would be interesting to see if XP apps work on Win 9x

File: Снимок.png (15 KB, 722x474)

15 KB PNG

Editing mergedcomponents\setupinfs\layout.inx seems to work.
Now im need to find file in mergedcomponents\setupinfs that has list of drivers to load.

Thought I would drop a few files fir changing Windows Setup Strings:

>srv03rtm\base\boot\setup\msgs.usa
language specific string for Windows Setup,
there are other msgs.* files are in that directory
for other languages

>srv03rtm\base\ntsetup\textmode\user\msg.mc
has strings for the textmode setup
(default usa/english build uses this)

>srv03rtm\base\ntsetup\syssetup\res.rc
Has some more strings to do with Windows Setup (GUI I think)

>base\ntsetup\billbrd\winntbb.rc
This file has the strings for the setup screen,
text like the "Try the easiest Windows yet"

>>78820933
might be txtsetup.inx

>>78804457 (OP)
> Windows XP/2003 Leak
Was the source code for Windows 9x ever leaked?

>>78821016
i wish

>>78820758
>>78821016
Try this on every 'sources.inc' file and see if you can replace Win98 binaries with these! lol

>>78818464
Can we have a creampie version?

Anyone know where to find Server2003 / SP1 symbolcd/dvd ISO?
I found some SP1 beta symbols ISOs, named like
>w2k3sp1_1247.IDS_usa_symboldvd.iso
>w2k3sp1_1260.IDS_usa_symboldvd.iso
>w2k3sp1_1433_usa_symboldvd.iso

Haven't been able to find the RTM/SP1 final versions though...

File: Снимок.png (34 KB, 722x470)

34 KB PNG

>>78820950
Yes it's fixed it

>>78821195
Ah, SP1 filename is en_windows_server_2003_symbol_dvd.iso
No sign of RTM symbols ISO though..

File: Снимок.png (16 KB, 642x554)

16 KB PNG

>>78821234
I hate winlogon...

>>78821255
The problem seems to be AMD64 can't launch winlogon process for some reason
our winlogon works fine with the official SP1 AMD64, so must be an issue with our AMD64 build

>>78821308
I only tried to use winlogon form xp server 2003 beta iso

>>78821308
To clarify, an anon got the same BSOD and tried testing stuff with winlogon, like making it DbgPrint as soon as it launches - DbgPrint never got sent though, showing winlogon never even got started, so there must be some issue starting the process for some reason.

Maybe it's something stupid like winlogon imports something from a DLL which wasn't included, dunno

>>78821331
Yeah it probably doesn't matter where winlogon came from, it'll give same BSOD no matter what, since the problem seems to be kernel/smss actually launching the process.

Any chance you can post the things needed for amd64 to get this far? I know winlogon-anon wanted to look into this, but there's no setups posted for amd64 to use...

File: file.png (139 KB, 1499x696)

139 KB PNG

>>78821248
>>78821195
Ah, found RTM symbols, pic rel
Doesn't seem they ever released them digitally on MSDN or anything, only as a physical disc

BA has them uploaded as
>2003-05 - 1011.2 - Windows Customer Support Diagnostics
It has pretty much same symbols.cab files as the .exe you can download from web.archive.org though, so not that interesting.

>>78821154
Cum is a completely different liquid from piss, so it'll probably have to be redrawn by someone with actual talent. The blood stuff was just changing the hue from yellow to red, but this would be much more difficult. I don't think anyone will be able to make a decent creampie one for a while.

I used :
https://gofile.io/d/UELj4P - fixed copywow64.cmd , fixed copytsc.cmd , modded layout.inx, modded txtsetup.inx

https://gofile.io/d/TNu97K - missing amd64 bins from AB1PXFRE_EN iso (missing.cmd not copied some files from iso like dmusic.sys, d3dpmesh.dll kodak_dc.icm, rtl39a64.sys

>>78821483
>>78821370

>>78821483
Ah awesome, many thanks
With those amd64.7z files in place, do you just need to build x86 and then amd64?

>>78821497
Yes first i built x86 then did postbuild. after that i started "bcz" building amd64

I just did a quick test, and cracked pidgen seems to work with win2k winlogon. Noticed that the win2k logon has some weird quirks and slows down the boot time, but it works

File: file.png (21 KB, 735x237)

21 KB PNG

>>78821511
good to hear, not sure why 2k winlogon would slow it down, but if you wanted to use original winlogon I think antiwpa2 should be able to get rid of product key checks inside it, at least the antiwpa nfo mentions that cracked pidgen he made works with it

File: Снимок.png (21 KB, 722x474)

21 KB PNG

Now im going to try debug amd64 installer

>>78821508
Nice, I'll give it a try later.
Was there any errors building amd64 after x86 tho? I remember someone mentioned you need to delete some file first when switching arch

>>78821530
Slow boot time might've been a fluke, but it also looks like the wallpaper only gets set on first logon, and it looks like fast user switching isn't implemented and doesn't work.

>>78821547
Also forgot to mention that oobe doesn't launch and it goes straight to the Administrator account, though this is really about the cracked pidgen.dll and not the win2k logon port.

>>78821559
Sorry for the spamming but I meant to say that I was really meant to test the pidgen.dll and not list issues with the win2k winlogon.

>>78821559
Hmm, you're testing per/pro SKU? none of the others use oobe after setup IIRC

>>78821543
delete inetsrv\iis\svcs\cmp\webdav\davcprox\fhcache_p.c
for some reason when im switching arch im not getting fhcache_p.c error anymore

https://gofile.io/d/RG239E (fhcache_p.c x86/amd64?)

>>78821595
Yeah, I was testing on pro.

>>78821599
>fhcache_p.c x86/amd64?
yeah midl-amd64 creates file that's both x86/amd64 compatible, some reason midl-x86 only makes an x86 version though
tried changing things around before so midl always used amd64 one but didn't have any luck with it
maybe it'd be a good idea to include this x86/amd64 combined fhcache_p.c into prepatched ZIP

Just added missing files to missingamd64fre.7z from AB1PXFRE_EN that missing.cmd missed
https://gofile.io/d/ch5Xmp

File: pic unrelated.jpg (109 KB, 736x747)

109 KB JPG

Updated x86-missing-binaries to v2, includes lang folder in both chk & fre, wasn't required for postbuild to succeed, but seems it's needed for ISO to closer match the official ones. (grabbed lang files from the official fre/chk ISOs)

Used missing-v8's lang folder as the list of files to copy from the ISO, should be correct for fre, but chk could need something extra maybe. I'll compare with official ISOs once I clean build fre/chk again.

Compared to missing-v8 there doesn't seem to be any files missing, only difference are files updated to XP SP1 version, and dpcdll/pidgen using enterprise instead of standard (because as explained in >>78808343 the only chk SKU is enterprise, seemed better to make fre/chk both match)

>win2003_x86-missing-binaries_v2.7z
https://gofile.io/d/SvWudI (link changed because gofile wouldn't let me edit the older one some reason...)

>>78821835
Nice, which edition/build did you get these from btw? the sp1 beta?

>>78821879
Oh you did mention AB1PXFRE_EN, seems that's 3790.1069 pro

>>78821879
Yes. 5.2.3790.1069.srv03_spbeta.030905-1850

>>78821903
>>78821908
If you want to get symbols for that build, the ISO name is
>srv03sp1_usa_1069_symcd2.iso
don't think they released any symbol EXE installers for it

>>78821016
They had to trash it after some sort of lawsuit. It will never be released unless someone stole it before then.

i am once again retooling the openxp repos: submodules edition
if someone can tell me what
SERVICES_DIR=$(O)
SERVICES_TAB=$(SERVICES_DIR)\services.tab

!if $(IA64)
LINK_LIB_IGNORE_FLAG=$(LINK_LIB_IGNORE_FLAG),4210
!endif


$(SERVICES_TAB): ..\services.tab
@echo Creating $@ from $**
$(C_PREPROCESSOR) $** > $@
means that would be nice

>>78822504
looks like $(O)\services.tab gets created by running ..\services.tab thru $(C_PREPROCESSOR)

>>78822548
huh, wonder why when running scorch services.tab is deleted then.

>>78822784
maybe another sources file creates the ..\services.tab file before this one runs, or something like that

>>78822802
yeah that's what i'm trying to figure out because without this tab file most of the core windows libs don't build.

>>78821483
>modded layout.inx, modded txtsetup.inx
Hmm, did you edit this by removing the lines of things that aren't in amd64, or did you add tags to the lines so they didn't get included in amd64?

>>78823041
ah nvm just checked, the lines were commented out
I'll try looking into adding tags to it later so they're marked as x86-only instead, that way x86 builds can still make use of them

>>78823035
whats the path to that file? seems there's a bunch of services.tab files

>>78823097
>>78823097
windows/core/kmode

>>78823165
oops sorry for that fuckup in format

im glad these thread are still here good job

>>78821857
>should be correct for fre, but chk could need something extra maybe
Just looked at chk, doesn't seem to be any missing files compared to official chk enterprise ISO, I'll try fre out later unless someone can get to it before me.

Is there any reason for people compiling chk?
What is the benefit to a chk build?

>>78823875
chk is better to debug with, has support for asserts and stuff

>>78823875
chk gives more info when debuging

Just tried build with PRERELEASE flag, didn't enable KD during setup though it seems sadly...
I swear I saw something about PRERELEASE setting up boot.ini with /debug flag too, but that didn't seem to happen neither.

Pressing F8 during text-mode setup when it says "setup is starting windows" does enable KD for text-mode though, but I'm not sure if it'll carry over to GUI mode setup

>>78824008
Hm, for some reason connecting KD to text-mode setup is making it hang at "Setup is starting windows" though.
WinDbg isn't breaking neither, weird, maybe it's something to do with mismatched baud rate? idk

>>78824031
Ah okay, default baud seems to be 9600 I think, seems connecting KD makes it take like 3 minutes extra to pass the "setup is starting windows" stage too.

If wanted you can edit SetupDebugOptions inside txtsetup.sif to change baud, eg.
>SetupDebugOptions = "/debug /baudrate=115200"

>>78824008
>>78824031
For GUI setup spamming F8 seems to work too, you'll get the menu from >>78821531's pic, choosing "debugging mode" seems to work with windbg set to 115200 baud, not sure if that's the actual baudrate windows is using though

>>78824226
GUI setup is slow as molasses with that though, guessing it's not 115200-baud

>>78823939
>>78823953
Thanks.

>>78824250
Seems default baud is either 19200 or 57600, depending on some ACPI table shit.
Editing KdCompInitialize inside base\boot\kdcom\xxkdsup.c should let you change the default, just change the mentions of BD_19200 & BD_57600 to BD_115200 instead

>>78805119
this actually

>>78804457 (OP)
Where's the media player source code?

File: 7322038.jpg (31 KB, 250x371)

31 KB JPG

>>78824426
multimedia\media\mplayer2

File: whistler 2410.jpg (116 KB, 1024x768)

116 KB JPG

Should try bringing the startpage code from XPSP1 over to server2003, all the code for this stuff seems to be there...

>>78824495
>from XPSP1
Give location, please.

File: file.png (51 KB, 857x221)

51 KB PNG

>>78824534
shell\explorer\desktop2\startpage.cpp etc.

win2003 removed startpage.cpp and all the references/resources for it, but it can probably be restored with XPSP1 code.
FEATURE_STARTPAGE seems to be the define that enabled it, if you search that in shell\explorer\ folder XPSP1 has a few hits for it

File: file.png (122 KB, 1639x997)

122 KB PNG

>>78824547
checking with winmerge shows the bits they removed for it.
eg. shell\explorer\initcab.cpp here

Added info about setup debugging to the guide:
https://rentry.co/build-win2k3#setup-debugging

Also updated the winlogon section to mention the DELAYLOAD change needed.

I'll update prepatched pack with the missing-ex-files tomorrow, will probably include the x86/x64 fhcache_p.c too, and update guide to use new x86-missing-binaries file from >>78821857

If there's anything else I should add there let me know.

>>78824031
Does textmode setup support network debugging? (kdnet)

If so there is a backported kdnet driver from windows 8 - https://github.com/MovAX0xDEAD/KDNET

File: only these network cards?.png (18 KB, 403x186)

18 KB PNG

>>78824684
It might do, seems you can set txtsetup.sif's "SetupDebugOptions" to any normal boot option like /debugport=NET, so might work fine.

I dunno if anyone tried the ported kdnet stuff with our builds yet though, also not sure if any VM uses any of the network cards it supports... since they're from win8 maybe there's something talking about using win8 kdnet with a VM

>>78824705
Ah the network card list is pretty big actually
docs.microsoft.com/en-us/windows-hardware/drivers/debugger/supported-ethernet-nics-for-network-kernel-debugging-in-windows-8-1
Need to check what vmware uses

File: file.png (9 KB, 397x181)

9 KB PNG

>>78824714
VMware seems to emulate Intel PRO/1000 MT adapter, looks like 2003 has the driver for it already too.
I'm not sure what the IDs are for it though, win2003 device manager won't show ID for some reason

>>78824746
driver inf for it is nete1000.inf, in there it seems PRO/1000 MT can be either 100E or 100F, and both are listed on that supported hardware page :)
maybe I'll give kdnet a try later on

txtsetup.sif has these lines that might be important -

SetupDebugOptions = "/debug"
OsLoadOptions = "/fastdetect /noguiboot /nodebug"

File: MitsuboshiColorsGlasses.png (161 KB, 1282x632)

161 KB PNG

>>78804521
wow

>>78824834
SetupDebugOptions is what gets applied when you hit F8 (needs to be spammed when it says "Press F6 if you need to install a third party SCSI or RAID driver")

OsLoadOptions are what it passes to kernel/loader by default, /nodebug gets removed when you press F8 though

>>78824250
>GUI setup is slow as molasses with that though, guessing it's not 115200-baud
fre build with the xxkdsup.c default baudrate changed to 115200 is a lot faster, that could just be because I'm using fre instead of chk though, I'll try another chk build with the 115200 change later.

>>78821530
>if you wanted to use original winlogon I think antiwpa2 should be able to get rid of product key checks inside it
Kinda surprised nobody's posted any winlogon.exe with that stuff already patched 2bh
Instead of going from 2003 winlogon -> cracked 2003 winlogon we skipped straight to 2000 winlogon instead...

>>78824250
I once built virtualbox from source and modified the serial port device to ignore baud rate. It was many times faster after that change.

Expanded the debugging section of the guide, added a small guide for enabling COM port on VMware too: https://rentry.co/build-win2k3#debugging

I don't mind adding other VM software too if someone writes a guide for them, doubtful anyone will but I figure it's worth asking...

File: file.png (51 KB, 918x249)

51 KB PNG

>>78825261
Added a section about un-filtering KD messages too, kernel can print a ton more KD messages when you enable components in registry (was hoping amd64 guy would try this to see if LDR can tell us why winlogon.exe wouldn't start, but he never did...)

https://rentry.co/build-win2k3#un-filtering-kernel-messages

>>78825163
"Generic Antiwpa-2.3-WinXP-2k3.ZiP" worked fine with the 2003 fre winlogon, detected it as "Windows 2K3(5.2) 3790.0 (Retail)", no error using cracked pidgen + all FFFFF key.

seemed to patch chk winlogon fine too but it didn't detect the version of it, no idea if it's working or not, I'll try a chk build later if nobody else gets to it

do you have debug symbols for vista beta?

Was there an option to increase the number of Threads given to razzle for compile? I recall there was an option but I don't remember what it was

anyone remember what i is?

>>78826290
build -M num maybe
can be used like
>bcz -M 4

How much binary shit is in the missing.7z? I noticed that a lot of it was pictures and shit, so I wanted to know how much important shit that needs to replaced is in there.

>>78826161
http://web.archive.org/web/*/https://msdl.microsoft.com/download/symbols/packages/*
lists pretty much all symbol downloads up to win8 there, make sure to use captures from 2006+

there's also "Customer Support Diagnostics" ISOs that have symbols for some betas they never posted as a download, dunno if those are hosted anywhere except BA though

>>78826352
A lot of it are drivers for ancient HW, MS themselves might not even have source for some of them.

>>78826382
Would it be possible to somehow disable postbuild's dependence on the less useful ones?

>>78826406
Yeah think someone posted a stripped down layout.inf before that removed the need for a lot of it, not sure if the install actually worked afterward though, pretty sure this was before we even had any build booting properly...

IMO we should probably try stripping things down so there's only stuff needed for most VMs to work, but I know there's some anons that say there's no reason to remove support for all that HW too

I guess it wouldn't hurt just to have a stripped-down one as an option though

>>78826358
longhorn beta 1 chk - didn't know there was CHK build, where to get it? :D

>>78826460
What build number of beta 1?

I found build 4050 chk if that helps
https://archive.org/details/windows-longhorn-build-4050.idx02

>>78826460
https://www.betaarchive.com/database/view_release.php?uuid=39b1778d-2cc2-4988-a014-03f122796005
https://www.betaarchive.com/database/view_release.php?uuid=1fc7e7b9-e4b9-4edb-894d-d1622cb0dbbc

there's a few longhorn chk builds, most of the builds MS released officially like 4051 had chk versions

>>78826530
that's pre-reset, beta 1 is 5112, i see there are symbols for chk, but never seen chk iso

>>78826535
6.0.5112.0.winmain_beta1.050720-1600_x86chk_client-professional_retail_en-us

this looks good, how to download it?

>>78826558
get BA access, or search the filename and hope someone mirrored it

>>78826535
>most of the builds MS released officially like 4051 had chk versions
weirdly it seems 4074 had amd64chk & ia64chk, but no x86chk...
bet some fag is probably hoarding that like all the other longhorn stuff, dunno why hoarders are so obsessed with it

VISTA BETAS AVAILABLE HERE -

https://winworldpc.com/product/windows-longhorn-vis/pre-reset

>>78826613
>▶
not chk builds

>>78826567
share it, more of us will take it

>>78826578
seems 4074 x86chk was leaked at some point, but is now a "lost build"
lh_usa_4074_x86chk_pro-dvd.iso was the iso name it seems, only seen 2 forum posts mention it, one comes up for "lh usa 4074 x86chk pro-dvd" and the other for "lh_usa_4074_x86chk_pro-dvd.iso"
crazy that people somehow lost a build MS themselves released...

>>78826613
Here is another one : https://archive.org/details/thelonghornarchive

>>78826696
yes but 5112 only FRE, no CHK build

>>78826812
Looks CHK is only on BA available

>>78826812
https://archive.org/download/6.0.5308.17.winmain-idx-01.060217-2200-amd-64fre-client-homepremium-business-bus/6.0.5112.0.winmain_beta1.050720-1600_x86chk_client-professional_retail_en-us-LB1PCHK_EN.zip

File: file.png (131 KB, 1011x1029)

131 KB PNG

>>78826642
>now a "lost build"
4074 chk was even released on MSDN with symbols too, seems those are lost now as well, damn...

If I download CHK build and CHK symbols - how to make use of it?

>>78826937

windbg or softice

>>78826921
Mental how many MSDN downloads are lost now

https://www2.hs-esslingen.de/~wohlrab/Complete_Download_Area.pdf
Just on this ancient listing I can see
>Prerelease: Windows XP Professional x64 Edition Build 1218 - Checked/Debug - (English)
>Windows XP Professional x64 Edition Check/Debug Beta, Build 1247 (English)
>Windows Longhorn Client Preview 2 - 32-bit Professional Edition Checked Build (English)
>Prerelease: Windows Server 2003 Enterprise x64 Edition with Service Pack 1 Build 1218 - Checked/Debug - (English)
All lost, like tears in rain, people really didn't care about checked builds it seems ;_;

>>78826937
Why you download stuff if you didn't know how to use it, lol.

>>78826937
slap that shit into IDA and get reversing

>>78826985
this shows what happens now? or can disassembly/decompile binaries?

>>78827022
I didn't ask about that LOL

>>78827036
Broh is to difficult to search online for answer? It is a debugger nothing more than that.

>>78826330

build seems to eventually freeze when you give it more than 2 CPUs to compile with

anyone else notice this?

>>78827237
no problems with 4 threads for me
sometimes it'll stall on mvdm/16bit crap for a little bit but it should eventually continue

>>78827286
You are using old prepatch now nvdm should be fixed, as the 16bit tools were build for x86

File: file.png (12 KB, 327x211)

12 KB PNG

>>78826921
>even 2004 winhec DVD was missing x86chk
sad, guess that explains why it's so rare, seems it was only on MSDN site, probably never gonna find it
WINHEC04_DVD2.iso does have longhorn install files on it, not sure if they're x86chk or not though, it's definitely not proper x86chk iso though since it also has ia64 & amd64 install files too

Anyone tried installing Vista in VirtualBox? I got BSOD 0x0000007E

>>78827595
Not sure if it's any help but there is a load of MSDN isos here, could be something worthwhile idk

archive.org/details/msdncds

File: Снимок.png (948 KB, 1154x938)

948 KB PNG

>>78827810
Vista works fine for me in VirtualBox

>>78828160
Where did you take this vista image from?
I'd rather not use W10 for that.

Remind me why people are now installing Vista and looking for Vista betas?

>>78828173
I Got it from webarchive but i can't find it anymore.
I still have torrent file https://gofile.io/d/q8ZrFo

>>78828225
because the are stupid.

>>78828403
>>78828225
And you're asking this question in the Friendly Windows XP/2003 Leak Thread.

>>78827237
I found out why compiler froze

I have my VM more than 4GB of RAM (was also testing PAE)
give it less than 4GB and it works fine.

>>78821308
>>78821255
>>78729928 →
>>78729928 →
>>78730123 →
>>78739979 →


Happens on winpe sp1 with our winlogon as well - someone posted an ISO and symbols for winpe sp1 which was BSOD'ing in the hope that the winlogon anon or someone else would debug it but nobody ever bit / did that - could very well be why amd64 is bsod'ing w/winlogon assert / exit.

>>78829131
the winpe issue was a different thing, the fix was posted right after that anon mentioned it >>78730123 →

>>78829234
well potential fix anyway, there's a chance SP1 amd64 ordinals & SP1 x86 ordinals don't match, haven't seen anyone check it

Bump

Why we look at XP SP1? XP and server are two different code bases, srv have security fixes that xp not have. If we miss stuff between those only bad things can happen. Better looking at the first sp1 beta of server 2003 that have and amd64 version.

>>78810005
Me and other anons have tried emailing you and got nothing back. Go neck yourself namefag

>>78830242
We looking at Windows XP amd64 version 2003(it's based on server 2003)

>>78830441
Windows XP amd64, does not exist. It should have never have been branded that way. NT 5.2 is windows 2003, the XP branding should be removed from the codebase.

>>78830441
again sp1 beta for srv support amd64 and is of course more near what we have.

>>78830481
i mean this https://betawiki.net/wiki/Windows_XP_Professional_x64_Edition_build_3790.1069

>>78829271
>>78830242
3790 AMD64 (x64) IS SP1 retail wise - if you want anything from the retail builds to work dll/exe wise and or WRK you need to have sp1 working which it does on x86.

>>78830406
Stop talking nonsense. I got just 3 mails so far and a lot of spam, including 2 mails from total noobs.
I am still waiting for messages and until I got more mails, I don't see any reason to respond, as there is no sense in creating community for 2 persons.

>>78810005
>>78831465
Are you trying to hijack all anons working on this here so other less knowledgeable users get nothing in the end?

File: accelerator_by_luisratedr(...).jpg (13 KB, 300x168)

13 KB JPG

Bump

Windows Longhorn build 4051 x64 chk.iso
https://archive.org/details/thelonghornarchive

>>78832750
This is XP thread!

figured out why service tables are deleted by scorch:
they're generated by gensrv in sdktools/
>>78834324
longhorn dbg/sdk is of direct use to use due to the close source.

Stop this Longhorn bullshit!

>>78834357
correction: no

>>78828160
Holy fuck I miss aero.

i'm just going to retire from like, trying to program on this for now and start doing repo maintainership stuff.

>>78835823
>and start doing repo maintainership stuff.
Nice. This is really needed.

File: Rest+in+cia+n_07d51e_7316495.jpg (133 KB, 1200x1165)

133 KB JPG

>>78831465

>>78831944
That's what it looks like. Fucking namefag.

>>78821511
How did you get it to work? I'm running the installer with W2K winlogon and the cracked pidgen.dll right now and when I enter random letters/numbers as a key, it says that it's an invalid key. Did you do anything other than put them in the tree and compile?

>>78837604
I used all F's as my key, I think it still checks if invalid characters are used in the key.

so amd processor driver is for example amd8k.sys what is the same for intel??
like amd8k.sys is the think we miss for amd64 in the srv codebase by the way.

Cracked pidgen.dll (must use with win2k winlogon):
>win2003_pidgenXP_cracked.zip
https://gofile.io/d/u5VOPp

>>78837604
Also, I used the new exinit/systime.c, but that wouldn't have made a difference.

>>78837682
Thanks.

File: file.png (327 KB, 1552x731)

327 KB PNG

After working on the Windows 10 compatibility for XP/2003, it looks like almost got (the compiled version of) Python 3.9 running in Windows XP, by making changes to KERNEL32.DLL and copying in 'downlevel' DLL's from Windows 10

But I am stuck now, I need help with a few remaining functions like GetActiveProcessorCount & GetLogicalProcessorInformationEx, so that I can properly test the code. Most of the things is implemented by using existing code from Wine, but for these I can't use Wine because it assumes Linux for retrieving CPU info.

Files are here https://gofile.io/d/l2OusB
Guide is here https://rentry.co/kernel32-extras

>>78838051
http://undocumented.ntinternals.net/index.html?page=UserMode%2FUndocumented%20Functions%2FSystem%20Information%2FNtQuerySystemInformation.html you might be able to get the info you need from here

>>78838051
well good luck you need to modify the kernel to add more stuff in, this is exactly why I told you that you were losing your time. Probably for the first you can use NtQuerySystemInformation and using some of the millions os possible pram you can get out of it

>>78838051
>Most of the things is implemented by using existing code from Wine, but for these I can't use Wine because it assumes Linux for retrieving CPU info.
I suggest you checking Wine from ReactOS's code.
They integrate some Wine dlls from time to time.
But don't know if this advice is any useful, I'm a codelet after all.

replied to the wrong thread but is there a way to get tabs in file explorer? having to open numerous windows all the time is stupid

Anyone have a link to the onion with the ida downloads

>>78838475
it's a scam, the good one that have also the amd64 decomps have install passwords....
And the one that don't have don't have the amd64 decompiler. Anyway this is the link http://fuckilfakp5d6a5t.onion/

>>78838508
I think you're supposed to read the readme for the password, I installed the 7.3 one from there not too long ago but reinstalled, it seemed to support amd64

>>78838590
in fact the 7.3 had the pwd in there I think the next ones only have the exe in the zip you download

>>78838590
>amd64
also the decompiler??

>>78838638
Looks like hexrays decompiler only works for x86, but ida itself can decompile amd64

>>78838450
wrong place
>>>/g/fwt

>>78838701
how you do that, I meean let IDA decomp amd64?

>>78838783
Open ida64.exe and feed it the file you're trying to decompile. Use the regular ida.exe for 32 bit files so you can use hexrays to decompile to C

>>78838701
IDA doesn't "decompile" dude... It disassemble, aka, generates lists in assembly language for the target architecture of the executable.

>>78838783
what he means is that even if hexrays doesn't work for amd64, you still can use IDA to disassemble the executables in amd64.

>>78838908
PD: it will be all in amd64 asm ofc.

A sources file contains an !ifdef.
How do I define something in a sources file?
I tried !define and it didn't work, spat out warnings.
Is there some sort of manual or guide for file formats included in this?
Documentation would be really nice.

>>78838051
PSUEDOCODE

int __stdcall GetActiveProcessorCount( short p1 )
{
unsigned int local_0x10; // [esp-16]
unsigned long local_0xC; // [esp-12]
unsigned short local_0x8; // [esp-8]
void * fs; // fs
int v1; // eax
void * v3; // edx
int v4; // ecx
int v2; // eax

v1 = GetProcessorGroupInformation( &local_0xC, &local_0x10 );
if( v1 == 0 ) {
v2 = 0;
} else {
if( (unsigned short)(v1 & 0xFFFF0000 | p1) == 65535 ) {
if( *(local_0xC + 10) != 0 ) {
local_0x8 = 0;
v3 = local_0xC + 33;
v4 = *(local_0xC + 10);
while( v4 != 1 ) {
local_0x8 = (unsigned short)local_0x8 + *v3;
(unsigned char *)v3 += 44;
v4 -= 1;
}
local_0x8 = (unsigned short)local_0x8 + *v3;
} else {
local_0x8 = 0;
}
} else if( (unsigned short)(v1 & 0xFFFF0000 | p1) < *(local_0xC + 10) ) {
local_0x8 = *(local_0xC + (unsigned short)(v1 & 0xFFFF0000 | p1) * 44 + 33);
} else {
RtlSetLastWin32Error( 87 );
local_0x8 = 0;
}
RtlFreeHeap( *(*((unsigned char *)fs + 48) + 24), 0, local_0xC );
v2 = (unsigned short)local_0x8;
}
return v2;
}

For GetProcessorActiveCount we might be able to do what wine does and just stub it to a function that returns the system core count. It should be obtainable through either NtQuerySystemInformation or GetSystemInfo.

>>78839966
GetActiveProcessorCount*